LMD VCL - Additional Infos (C++ User)

LMD 2016 VCL - Additional Infos (C++ User)
(© by LMD Innovative, (http://www.lmd.de or http://www.lmdinnovative.com)

How to use LMD VCL packages in C++ Builder
Please make sure that following conditions are valid:

IDE has knowledge of location of LMD *.hpp files. In C++ options within Tools|Environment options-dialog Search/Include path settings must contain location of LMD VCL lib/source files. If this condition is not met, compiler/linker can not access header files (this is e.g. cause of problem, when IDE adds only *.h files to header files of your units when LMD-Tools components are added onto your forms).
Because of the fact that no longer *.obj files are shipped in precompiled packages, you have to make sure that *.lib file of the packages you want to use can be referenced by the IDE.
If you get a "Can't find XXXXX.obj" linker error, IDE has NO access to required lib file (error message does NOT mean, that actually *.obj files are required. Simply make sure that LIB files can be accessed by IDE. This can be done by specifying correct project option settings OR adding the corresponding *.lib file to your project).

WebPack and TextPack notes

WebPack: If you encounter linker errors like [Linker Error] Unresolved external "InternetCloseHandle" referenced from...
Simply add wininet.lib to your project (file can be found in \lib directory of your C++ Builder / BDS / CRS installation). In recent IDEs you can also add
#pragma link "wininet.lib" in your code.
TextPack: When Runtime Packages are used (Project options, "Build with runtime packages"), it must be assured that lmdparse4rt_XX (XX represents the compiler version) is mentioned before the TextPack packages. Otherwise an exception during application start will occur.